Skip to content

Conversation

Harrm
Copy link

@Harrm Harrm commented Oct 15, 2025

Description

Introduce archive storage for historical data (data older than N blocks).

Integration

Review Notes

TODO:

  • Child storage
  • Iteration
  • Benchmark archive storage performance and size
  • Add collision prevention for concatenated key+block number keys
  • Mock merkle root calculation for re-executing historical blocks

Checklist

  • My PR includes a detailed description as outlined in the "Description" and its two subsections above.
  • My PR follows the labeling requirements of this project (at minimum one label for T required)
    • External contributors: Use /cmd label <label-name> to add labels
    • Maintainers can also add labels manually
  • I have made corresponding changes to the documentation (if applicable)
  • I have added tests that prove my fix is effective or that my feature works (if applicable)

Bot Commands

You can use the following bot commands in comments to help manage your PR:

Labeling (Self-service for contributors):

  • /cmd label T1-FRAME - Add a single label
  • /cmd label T1-FRAME R0-no-crate-publish-required - Add multiple labels
  • /cmd label T6-XCM D2-substantial I5-enhancement - Add multiple labels at once
  • See label documentation for all available labels

Other useful commands:

  • /cmd fmt - Format code (cargo +nightly fmt and taplo)
  • /cmd prdoc - Generate PR documentation
  • /cmd bench - Run benchmarks
  • /cmd update-ui - Update UI tests
  • /cmd --help - Show help for all available commands

You can remove the "Checklist" section once all have been checked. Thank you for your contribution!

@cla-bot-2021
Copy link

cla-bot-2021 bot commented Oct 15, 2025

User @Harrm, please sign the CLA here.

@bkchr
Copy link
Member

bkchr commented Oct 17, 2025

Introduce archive storage for historical data (data older than N blocks).

Why is this a completely separate db and not just a special column? Or just stored under special keys in the existing state column?

@Harrm
Copy link
Author

Harrm commented Oct 17, 2025

Introduce archive storage for historical data (data older than N blocks).

Why is this a completely separate db and not just a special column? Or just stored under special keys in the existing state column?

Currently it's indeed just a new column space in RocksDB, internally.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants